Web content authoring is the process of creating page-level content for your Content Management (WCM) websites. Web content authoring comprises the following activities:
■ Defining the content records that populate the content areas of your website pages, optionally using workflow and Surf-to-Edit features to help with this task.
■ Managing images that you use in your content.
Before you begin
You cannot perform web content authoring tasks until after the people in your organization who perform website management have performed the following tasks:
■ Defined content authority groups (CAGs) to control who can define/approve content records and upload images and other file types for use in content records
■ Defined content folders in which to create your content records
■ (optional) Assigned CAGs to specific content folders to enable workflow for the content records in that folder
■ (optional) Defined tags and tagged list formats for use in your content records
■ (optional) Defined CM user defined fields (UDFs) for use in your content records
Putting it all together
Web content authoring entails the following actions, performed as needed:
■ Managing content records, each of which is the source of a content area on a rendered web page. You can define these on an ad hoc basis as needed, or by tracking your current and available authoring work in your Content Designer Task List.
□ You revise pages for your website by adding one or more iParts to a content record and/or configuring existing iParts in the content record. Save the changes and then Publish the content record. A few minutes later, the changes become live on all CM websites that use that content record. (You might need to refresh the page in your browser to see the changes.)
□ If you're creating a brand new page, you must link the content record to a navigation item in the website's sitemap to add the published content record to the website. This is typically done by the person who manages the website.
□ There are standard iParts that come with CM, and the people who implemented your CM environment might have added some custom iParts too. To learn about the standard iParts and what they do, see Fields: iParts gallery.
■ Managing images for use in content records.
■ Approving content records for publication or deletion by authors who do not have Content Approver permissions.
■ Browsing your website to review its content and using Surf-to-Edit (see Revising website content with Surf-to-Edit) to the underlying content records (or to log a change request for a content revision if you do not have Content Editor permissions for a given content record).
Note: Full users can perform all web content authoring tasks from the Web view of iMIS. Full, Casual, and Public users can define and revise content by using the Surf-to-Edit feature of CM.